home *** CD-ROM | disk | FTP | other *** search
- Subject: Re: another 1.10 job control bug?
- Date: Tue, 8 Mar 1994 09:34:15 -0500 (EST)
- From: Chris Herborth <herborth@53iss6.waterloo.ncr.com>
- In-Reply-To: <Up-ECGMAJAT@asharak.apana.org.au> from "michael smith" at Mar 6, 94 12:20:40 pm
- Message-Id: <9403080935.aa18147@ncrhub1.NCR.COM>
-
- What you wrote:
- > % frob datafile
- > ...
- > ^Z
- > {% bg}
- > % logout
- >
- > I would expect to get a message indicating that there are stopped
- > {backgrounded} jobs. (probably from the shell being polite)
- >
- > If I were to do :
- >
- > % frob datafile &
- > % logout
- >
- > Then I would expect to be able to logout and know that frob is running
- > happily without a tty, and not laying claim to mine.
-
- On the SysV boxes here, you have to:
-
- bash% nohup frob datafile &
- bash% ^D
-
- Otherwise the process is terminated as soon as you log out AND kill your
- telnet; telnet from my box stays attached to the SysV box until I kill
- it if there are running processes.
-
- Just FYI... Things don't seem to work they way we'd like 'em, even on
- "real" UNIX.
-
- > Bop me one if I'm barking up the wrong tree here, but once the user
- > indicates that they're leaving, the tty should be free. If there
- > are processes that think that it's still theirs, this is a bug.
-
- I don't know if the tty stays on the SysV box, but as far as my local
- machine is concerned, the connection is still valid.
-
- --
- ----------========================_ /\ ============================----------
- Chris Herborth \`o.0' herborth@53iss6.Waterloo.NCR.COM
- Information Products Developer =(___)=
- AT&T Global Information Solutions U
-